table lock

RR does not allow phantom reads by creating an S ( share) table lock when selecting rows.

RR不允许幻象读取，它会在选择行时创建一个S（share）表锁定。

Enterprise Manager might display TM for any table lock, rather than indicate the mode of table lock ( such as RS or SRX).

每种锁类型或锁模式后面的圆括号里面的缩写，被用在企业管理器的锁监控器软件上。

This is because the new X row lock and the IS table lock are not compatible.

这是因为新的X行锁定和IS表锁定是不兼容的。

When a table holds an IX lock, the lock owner and concurrent applications can read and update data in that table.

当表持有IX锁时，锁拥有者和并发应用程序可以读和更新该表中的数据。

Using the Repeatable Read isolation level may result in an automatic table lock in some cases.

使用可重复读隔离级别在某些情况下可能会导致自动执行表锁定。

Searching on Page Level Lock, Table Level Lock and Dead Lock on the Basis of SYBASE SQL Server

基于Sybase SQL Server的页锁表锁及死锁研究

The only alternative to a lock on every new row is a table lock ( since there are no page locks in DB2).

对于每个新行之上的锁，惟一可以替代的是表锁（DB2中没有页锁）。

The hang is caused by an exclusive row lock on table EMPLOYEE.

挂起是由表EMPLOYEE上一个独占式的行锁导致的。

The S lock allows concurrent applications that use read-only queries to access the target table, but applications attempting to write data to the table are prevented from doing so.

S锁允许使用只读查询的并发应用程序访问目标表，但是防止应用程序写数据到表中。

The database manager determines which locks to escalate by looking through the lock list for the application and finding the table with the most row locks.

数据库管理器通过查看应用程序的锁列表并查找行锁最多的表，来决定对哪些锁进行升级。

The workmen even made me two little chairs and a table ， and a lock for the door ， so that no rats could get in.

工匠甚至还给我做了两个小椅子和一张桌子，一把门锁，这样老鼠就进不去了。

Db2pd reports a lockwait situation for a row lock occurring on table with ID6 in tablespace with ID2.

db2pd报告ID为2的表空间中一个ID为6的表上有一个行锁存在锁等待情形。

When using CS in application A1, there will be an IS ( intent share) table lock.

在应用程序A1中使用CS时，将有一个IS（intent share）表锁定。

If after replacing these with a single table lock, the MAXLOCKS value is no longer exceeded, lock escalation stops.

如果用一个表锁替换这些行锁，将不再会超出MAXLOCKS值，那么锁升级就会停止。

In some database management systems, the optimizer may choose to take a table lock immediately based on the expectation that lock escalation is likely to occur.

在某些数据管理系统中，优化工具可以根据可能出现的锁升级要求来立即对某个表加锁。

If a transaction obtains a row lock for a row, the transaction also acquires a table lock for the corresponding table.

如果一个事务获得了一行的行锁，那么这个事务同时获得了相关的表的锁。

Because the acquired lock does not persist across transaction boundaries, the import utility loses its IX table lock and must request another lock after each commit.

因为获得的锁不会跨事务边界存在，所以import工具将失去它的IX表锁，并且必须在每次提交之后请求另一个锁。

Even with low-level testing involving a small number of connections and small volumes of data, this can cause lock escalations from row to table locks, resulting in locking problems.

即使对于只涉及少量连接和数据的低级测试，这都会引起从行锁到表锁的锁升级问题，从而导致锁定问题。

When using UR in application A1 on selecting multiple rows, there will be an IN ( intent none) table lock on the accessed table.

在应用程序A1中使用UR来选择多行时，所访问的表中将有一个IN（intent none）表锁定。

After some small number of row locks are obtained, a lock escalation to a table lock will occur automatically.

当获得少量的行锁时，行锁就会自动地逐渐升级为表锁。

Information about the lock that was requested by the waiting application, such as row or table lock, shared or exclusive lock, table name, and so on.

等待应用程序请求的锁信息，如行或表锁、共享或独占锁、表名等等。

For table spaces containing more than one table, when DB2 acquires locks on a table, that lock does not affect access to segments of other tables.

对于包含多个表的表空间，当DB2取得用于某一个表的锁时，这个锁不会影响对其他表的段的访问。